Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1662

reference: 377-tree-1
name: 1662
tree-preservation-order: undefined
377-tpo-1
uprn
address-text
point: POINT (-1.024188 50.882352)
geometry: MULTIPOLYGON (((-1.024103 50.882343,-1.024107 50.882360,-1.024119 50.882375,-1.024137 50.882387,-1.024161 50.882395,-1.024187 50.882398,-1.024214 50.882396,-1.024238 50.882388,-1.024257 50.882376,-1.024269 50.882361,-1.024274 50.882345,-1.024270 50.882328,-1.024258 50.882313,-1.024239 50.882301,-1.024216 50.882293,-1.024190 50.882290,-1.024163 50.882293,-1.024139 50.882300,-1.024120 50.882312,-1.024108 50.882327,-1.024103 50.882343)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL